Skip to main content
Version: 6.0

Release Notes

The first version of the new 6.x series brings numerous improvements and new features.


New features in the UI in general

FS#2105 – Translation of the UI into French

From version 6.0 onwards, TimePunch is also available in French.

New features in the self-reporting section

FS#2056 – Request system for forgotten or incorrect entries

Changes to time entries or forgotten entries can now be requested via the self-reporting section. Employees submit a correction request (e.g. for ‘arrival/departure’ or project times). Approval is then given by the direct supervisor in TimePunch Management.

New functions in the framework times / Cutter

FS#2098 – Mandatory break for forgotten break entries

A mandatory break can now be stored in the framework times, which automatically takes effect if a break has not been entered. This mandatory break is independent of the statutory minimum break after six hours of work and is intended to encourage employees to book their breaks independently.

New functions in the calendar / Calendar

FS#2016 – Display of request information (‘Submitted on’ / ‘Approved on’)

For absence requests, the request date and the approver are now also displayed directly in the overview.

New functions in administration / management

FS#2097 – New report ‘Working time, weekly hours’

A new report clearly displays working hours, overtime, flexitime and holiday – broken down by days, weeks and months – for each employee.

FS#2071 – Assignment of project employees also via the project dialogue

Employees can now also be assigned to projects directly via the project dialogue – for persons with the appropriate position of trust. The prerequisite is that these employees are stored as project managers or assistants in the respective project.

New functions in the backend

FS#2091 – Automatic closing of time entries after a certain period of time

Open time entries – for example, due to forgotten logouts – are now automatically closed after a maximum of 16 hours of working time.

FS#1398 – New ‘booking date’ field to avoid errors with shift times

TimePunch now has a new internal field called ‘booking date’. This determines which calendar day a time entry is assigned to. If a time entry logically still belongs to the previous day's shift, the booking date may differ from the actual login date.

The following bugs have been fixed

  • FS#2090 – Overwriting of half days in case of double requests
  • FS#2096 – Splitting time sheets into working time sheets and project hours
  • FS#2085 – Inconsistency when creating time entries
  • FS#2084 – Sick (doctor's appointment) should also be able to be started online
  • FS#2083 – Sick (doctor's appointment) should also be able to be started via the Watcher
  • FS#2082 – ‘Data protection coordinator’ authorisation corrected

Focus instead of ballast: TimePunch Legacy is being discontinued

With version 6.0, we are saying goodbye to the outdated TimePunch Management Client (4.x). We deliberately included it in 5.x to facilitate the transition to the new UI. However, our evaluations clearly show that the legacy version is hardly used anymore. Good for everyone: we are investing the freed-up resources in new features and your customer requests.